What changed

• recognize standalone ::codex-inline-vis{file="..."} directives outside fenced code
• resolve native Codex visualization fragments through a schema-validated WebSocket RPC
• securely derive the thread-scoped Codex path, reject symlinks and files over 5 MB, and avoid exposing filesystem paths to clients
• render interactive fragments in a theme-aware allow-scripts iframe without allow-same-origin
• add dynamic height, bounded client caching, loading/error states, external-link confirmation, streaming-tail suppression, and copy cleanup

Why

The native Codex Visualize skill emits an HTML fragment plus an inline directive. Threadlines previously passed that directive through ordinary Markdown, so users saw raw text instead of the interactive result.

User impact

Codex visualizations now appear directly at the directive position in chat while preserving surrounding Markdown. Other providers and malformed directives remain unaffected.

Validation

• vp fmt
• vp lint
• vp run typecheck
• vp run @threadlines/contracts#test orchestration
• vp run @threadlines/web#test ChatMarkdown
• vp run @threadlines/web#test MessagesTimeline.logic
• vp run @threadlines/web#test wsRpcClient
• vp run @threadlines/server#test CodexHomeLayout
• vp run @threadlines/server#test ws
• vp run @threadlines/web#test:browser ChatMarkdown